for science teams
A lightweight workflow structure for software development which is characterized by 4 key features.
Term is traced back to the 2001 Agile Manifesto, but the ideas are much earlier and broader. Very related to Lean Methodology (aka Toyota Way).
Important
Agile methods are ubiquitous in software developement. This is how modern teams work because it Drives Creation and Completion
A key principle: dividing work into 10-30 day chunks with plan and review (or check) elements
Adopt habits that organically improve team flow and efficiency.
team awareness fundamentally changes the team dynamic
forces work to be iterative and incremental
helps team define a minimally complete chunk of work that can be reviewed
quickly reveals bottlenecks and barriers
Keeping the team task board fresh won’t happen by itself. Everyone get pulled into their own rabbit hole and then team becomes silo-ed.
Daily Standup
time-boxed 15 minutes
what I did yesterday, what I plan to do today, any barriers
a designated team facilitator runs this
done around the task board
can be done asynchronously but much better if it is live
gets the team in flow
Most popular and widely used method in software development, but not restricted to software at all.
Formalizes the workflow cycles and events
Roles
Artifacts
Product Owner Works on the backlog and gets tasks ready for next sprint.
Scrum Master
Team
1 In a science context, this might be a presentation outside of the team. Formal enough that you need to do a good job.
Scrum in software dev is used to speed up development cycles. Velocity and measuring the size of tasks is a key part of Scrum in this context.
Atlassian Kanban video series
These cover the basic elements
5 minute intro to Scrum Basic Structure of Scrum
12 minute intro to Scrum Product development perspective